Skip to content

Update CI, docs and repo scripts for the genome split (6/6) [PILOT-9071] - #4379

Merged
RaduAna-Maria merged 11 commits into
mainfrom
feat/genome-stack-6-planner-cleanup
Nov 12, 2026
Merged

RaduAna-Maria merged 11 commits into
mainfrom
feat/genome-stack-6-planner-cleanup

Conversation

@RaduAna-Maria

@RaduAna-Maria RaduAna-Maria commented Nov 3, 2026 •

Copy link
Copy Markdown
Collaborator

Issue

PILOT-9071

Stack 6 of 6 (#4327 → #4328 → #4329 → #4330 → #4358 → #4379), merged together.

Summary

  • CI runs the genome checker tests with Node; required job names unchanged
  • Move Studio Web command ceilings from uipath-genome to uipath-build-from-genome
  • Remove the uipath-genome docs

Testing (stack top)

  • validate, links, registries, sensitive-content scan, 244 planner + builder pytest: pass
  • Failing on main too: maestro-case CLI snapshot test; Studio Web ceilings for agents / solution / test

🤖 Generated with Claude Code

@github-actions

github-actions Bot commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @RaduAna-Maria's task in 3m 27s —— View job


Summary

This PR is the last of the six stacked genome PRs. It resolves contradictions in the planner guides and templates: package versions, gap markers, deploy routing, HITL routing and the Platform constraints row. It gives each repeated rule one home. It also splits product-selection-guide.md into a new design/scope-recommendation-guide.md plus a "Resolving the Delivery Model" section in platform-availability-guide.md, folds each skill's parts-guide.md into its execution or extraction parts guide, and renames the lane-era tasks.

Most of the consolidation is clean. Nothing still links to the deleted parts-guide.md files, the moved product-selection-guide.md sections or the moved design-guide.md Step 0 anchor, and no stale lane_a / lane_b names are left anywhere. Removing the "soft second factor is scripted" bullet from pdd-analysis-guide.md also fixes a real contradiction with attended-reauth-pattern-guide.md, which says "never by default". Four issues are worth fixing before merge; all are in uipath-planner.

Change-by-Change Review

1. skills/uipath-planner/references/plan/plan-guide.md:88 — a routing row landed in the wrong table

Medium. The "Single-host SDD with absorbed components" row was moved out of the routing table this PR deletes from multi-skill-patterns-guide.md. It was inserted into the "Template | Project list location" table (Step 3) instead of the Step 4 "SDD shape | Pattern" table. That table now has a row whose second column is a routing rule ("Leaf-first … no orchestrator task"), not a section location.

Step 4 is now the only home for pattern routing (multi-skill-patterns-guide.md points there), so this rule has effectively left the routing table. An agent picking a pattern for an RPA host that consumes an IXP model or a connector won't find it.
Fix this →

2. skills/uipath-planner/references/decompose/decompose-guide.md:98 — Q2 skip default now contradicts its own recommended option

Medium. When Q2 (Execution autonomy) is skipped, the default changed from autonomous to interactive. But the question body at :126 still marks Autonomous to completion as *(recommended)*, and design-guide Q1 also recommends Autonomous. So the guide now says "recommend autonomous" and "default interactive" in the same place — the kind of contradiction this PR set out to remove.

This is also a behaviour change for every doc-less decompose run that skips Q2. The PR summary doesn't mention it, and coder-eval wasn't run. Pick one: revert to autonomous, or keep interactive (it matches plan-guide.md:50's "safer" default for a missing handoff field) and move the (recommended) marker. Either way, say so in the PR body.

3. skills/uipath-planner/references/decompose/decompose-guide.md:24 — the Read Plan still points at the moved preflight table

Medium. The Step 1 sub-step 5 row still reads "[design-guide.md] § Step 0 (the preflight host table)". This PR moved that table to platform-availability-guide.md § Resolving the Delivery Model, and the Step 1.5 body (:71) was updated to say so. Following the Read Plan, the agent opens design-guide.md Step 0 and finds only a one-line pointer.
Fix: replace the design-guide entry with platform-availability-guide.md § Resolving the Delivery Model. That file is already on the row, so the change is just dropping the design-guide part.

4. skills/uipath-planner/references/design/design-guide.md:38 and :59 — the Read Plan loads the delivery-model guide too late

Medium. Phase 1 Step 0 now says to run platform-availability-guide.md § Resolving the Delivery Model first, before the entry prompt. But the only Read Plan row for that guide is triggered at Phase 1 Step 4. If the agent follows the Read Plan, it reaches Step 0 without the preflight table, Question 2 or the skip rule. Before this PR they were inline, so this is a regression.
Fix: add a Read Plan row | Phase 1 Step 0 | — | platform-availability-guide.md § Resolving the Delivery Model |, or change the existing row's phase to Step 0.
Fix 3 + 4 →

5. skills/uipath-build-from-genome/references/execution-parts-guide.md — item cross-references after the merge

Low. The intro says "An item number refers to its own section unless another section is named." Two problems follow from that:

  • Anti-patterns 1–2 cite "(items 3, 4)" and "(items 5, 7)". These were parts-guide.md items and now live under § Running in Parts. But § What a Build Adds has its own items 3, 4, 5 and 7 (Object Repository linking, progress, solution mutations, the report), and the Anti-patterns section has no items of its own. Fix: write "§ Running in Parts items 3, 4".
  • Item 8, the Subagents options, still says "as many parts at once as the mode's parts guide lets run in parallel". The mode's parts guide is now this file. The extraction twin was updated to "§ What Extraction Adds", so this should read "§ What a Build Adds item 1a".

6. skills/uipath-planner/references/design/scope-recommendation-guide.md:13-19 — template paths are wrong for the new location

Low (inherited from the old file). Template Mapping lists ../assets/templates/*.md. From references/design/ that resolves to references/assets/templates/, which doesn't exist; the correct prefix is ../../assets/templates/. They're code spans, not links, so check-links doesn't catch them. The move is a good moment to fix them.

7. skills/uipath-planner/assets/templates/rpa-sdd-template.md:650-651 — placeholder style

Low. <Latest, or the version the PDD names> breaks the repo's <UPPER_SNAKE_CASE> placeholder convention. Suggest <LATEST_OR_PDD_VERSION>; the blockquote above already states the rule.

8. Everything else — OK

  • Templates: the Platform constraints row is now in all six non-case Decisions Made tables, and the non-RPA comment matches sdd-writing-guide.md Step 2 item 3. The HITL routing comments are gone. The package-version rule is consistent across rpa-sdd-template §14 and package-selection-guide Pitfall 1.
  • Deploy routing: the "outside a solution → uipath-platform, inside → uipath-solution" rule is consistent across multi-skill-patterns-guide, Pattern 1, and the new decompose Packaging: header field.
  • Source framework = UiPath: consistent across extracted-genome-guide, process-genome-template, the builder's genome-reading-guide, and the salesforce genome example that test_genome_check.py uses.
  • Partial Re-extraction moved cleanly into extract-guide, and the edit-guide, extracted-genome-guide and extract-guide anti-pattern 19 pointers were updated.
  • Rules that left SKILL.md or design-guide.md each still have one home:
    • "Review After Every Write" → extract-guide Step 7, edit-guide § Review after every edit, and genome-format-guide Writing Rule 13.
    • The case reading set and "never cat" → case-design-guide.md:17.
    • "Building from a genome here" → Critical Rule 3.
  • Flavor overrides: the non-pdd-plan-reference → decompose-plan-reference marker rename is applied to both the canonical file and the Studio Web override, and no orphan names are left.
  • allowed-tools: the new WebSearch entry is backed by platform-availability-guide Gating Rule 4 (web-search the availability page).
  • Task renames: the lane.txt → verb.txt changes are consistent across file_exists, file_contains and run_command. CODEOWNERS covers the renamed dirs through /tests/tasks/uipath-planner/.

What's Missing

  • coder-eval was not run (the PR says so). Phase 1 and the template text are agent-facing, and the decompose Q2 default changed (item 2). At least smoke_decompose_activation, plan_marker_detect, plan_task_derivation and one design task should get a passing-run claim before merge (.claude/rules/test-writing.md step 5).
  • The PR body doesn't list two behaviour changes: the decompose Q2 skip default (autonomous → interactive), and the decompose Delivery model header field becoming mandatory.

Area Ratings

Area Status Notes
Frontmatter OK Only change: allowed-tools gains WebSearch (justified); description untouched
E2E Tests Issue Renames are clean; no coder-eval run for agent-facing changes
Skill Body OK SKILL.md trimmed to routing; the removed rules still have a home
References & Assets Issue Items 1–4 (Medium), 5–7 (Low)
Repo Hygiene OK CODEOWNERS entry for the deleted file removed; no secrets or personal paths; no cross-skill file reads

Issues for Manual Review

  • Whether the decompose Q2 default (interactive) is the intended product decision. It conflicts with the (recommended) option and with design's Autonomous recommendation.
  • Changing the task_ids breaks the run history for these tasks on the codereval dashboard (the PR flags this).
  • Whether uipath-api-workflow really always deploys through uipath-solution (plan-guide Step 4) under the new "the deploy skill follows the packaging" rule.

Conclusion

Request changes (minor). The consolidation is sound and removes real contradictions. Fix items 1–4 before merge; three are one-line pointer or table moves, and item 2 needs a decision. Items 5–7 are optional polish. Please also add a coder-eval run for the decompose/plan smoke tasks.

@github-actions

github-actions Bot commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @RaduAna-Maria's task in 1m 33s —— View job


Coder-eval task lint (advisory)

This PR changes 11 task YAMLs (5 renamed, 6 with edits to comments only). Verdicts: 0 Critical, 0 High, 2 Medium, 3 Low, 6 OK.

Rubric: .claude/commands/lint-task.md. This check is advisory and never blocks merge.

Evidence of passing run

  • ❌ High — The PR body says "coder-eval not run". The renames change five task ids (skill-planner-integration-decompose-*, skill-planner-smoke-plan-marker-detect, skill-planner-plan-task-derivation, skill-planner-smoke-decompose-activation). Two of these tasks now write verb.txt instead of lane.txt. Phases 1 and 4 also change the product-selection and template text these tasks grade. Please edit the PR description to add a line like: Ran plan_marker_detect, smoke_decompose_activation, plan_task_derivation, decompose_* locally and they passed.

Per-task lint

tests/tasks/uipath-planner/plan_marker_detect/plan_marker_detect.yaml — verdict: Low (theme-captured; see Theme 1)

tests/tasks/uipath-planner/smoke_decompose_activation.yaml — verdict: Medium

Issues:

  • [Medium] Could pass for the wrong reason: L10-19 forbid building and forbid writing an SDD or task list, but no criterion checks either. The only checks are skill_triggered plus verb.txt (Theme 1).

Suggested fixes:

  • Add the no-artifacts guard that plan_marker_detect.yaml:54-60 already uses, extended to SDDs: ! find . \( -name '*-tasks.md' -o -name '*-sdd.md' -o -name '*.xaml' -o -name '*.flow' \) -not -path '*/node_modules/*' | grep -q . (weight 1.0).

tests/tasks/uipath-planner/decompose_dispatcher_performer_plan.yaml — verdict: Medium

Issues:

  • [Medium] Meaningful coverage: there is no skill_triggered criterion, although the description (L5) says the task "must engage the planner". A non-planner agent that writes the right tokens passes.
  • [Low] Could pass for the wrong reason: the uipath-solution check at L44-50 is a bare substring, so a line like "not uipath-solution" still passes. The description at L6 still says "uipath-solution / uipath-platform", while the criterion (and this PR's routing rule "inside a solution → uipath-solution") wants only uipath-solution.
  • [Low] Meaningful coverage: L58 accepts Testing (MANDATORY) anywhere in the file, and pass_threshold: 0.75 lets it be missing entirely.

Suggested fixes:

  • Add a skill_triggered criterion for uipath-planner (weight 2.0), as in plan_genome_pattern7.yaml:32-37.
  • Replace L44-50 with run_command: grep -Eq '^#+ *Task T[0-9]+.*uipath-solution' rpa-build-plan.md. Change L6 to "route the deploy step to uipath-solution".
  • Move the Testing check into its own run_command: grep -qE '^#+ *Task T[0-9]+.*Testing.*\(MANDATORY\)' rpa-build-plan.md. This is the same check decompose_multiskill_plan.yaml:58 uses.

tests/tasks/uipath-planner/decompose_multiskill_plan.yaml — verdict: Low

Issues:

  • [Low] Meaningful coverage: there is no skill_triggered criterion, although the description (L4) says the task must "engage the planner".

Suggested fixes:

  • Add a skill_triggered criterion for uipath-planner (weight 2.0).

tests/tasks/uipath-planner/plan_task_derivation/plan_task_derivation.yaml — verdict: Low

Issues:

  • [Low] Could pass for the wrong reason: the regex at L76 is testing|test case|uipath-test and matches the word "testing" anywhere, including in the copied SDD path or in prose. It does not check for a dedicated Testing task.
  • [Low] Meaningful coverage: there is no skill_triggered criterion.

Suggested fixes:

  • Tighten L76 to grep -qE '^#+ *Task T[0-9]+.*Testing' vendor-payment-sync-tasks.md. This also matches the Testing rule that this PR consolidates into shared/plan-and-tasks-format.md.
  • Add a skill_triggered criterion for uipath-planner.

tests/tasks/uipath-planner/plan_genome_pattern7/plan_genome_pattern7.yaml — verdict: OK

tests/tasks/uipath-planner/author_component/author_component.yaml — verdict: OK

tests/tasks/uipath-planner/extract_component/extract_component.yaml — verdict: OK

tests/tasks/uipath-planner/extract_solution/extract_solution.yaml — verdict: OK

tests/tasks/uipath-planner/genome_from_sdd/genome_from_sdd.yaml — verdict: OK

tests/tasks/uipath-planner/genome_from_solution_sdd_case_child/genome_from_solution_sdd_case_child.yaml — verdict: OK

Within-PR duplicates

  • No duplicate clusters detected. The PR adds no new task content; the 5 renamed files keep their existing criteria.
  • The renamed tasks still differ from their nearest siblings in what they test:
    • plan_marker_detect vs plan_task_derivation: the first checks only that the verb is detected, the second derives the full task list.
    • smoke_decompose_activation vs decompose_multiskill_plan: the first checks activation, the second checks the emitted plan.

Themes

  • Theme 1 — the verb name is graded from a file the agent writes (Medium). plan_marker_detect.yaml:21-52 and smoke_decompose_activation.yaml:18-41 ask the agent to write the verb it chose to verb.txt, then grade that file. That is close to the self-report pattern ("a results file with your decisions"). It is softened by the skill_triggered gate, and nothing else the agent does reveals the routing choice in a smoke test. The pattern predates this PR (lane.txt → verb.txt).
    • Consider giving the verb.txt checks less weight than the skill_triggered and no-artifact checks.
    • Or check that the agent read the verb's reference file, e.g. a command_executed with tool_name: Read matching references/plan/plan-guide.md or references/decompose/decompose-guide.md.

Notes (outside the rubric, comment-only):

  • genome_from_sdd.yaml:81 still says "The Author lane", in a PR that removes lane-era names.
  • extract_solution.yaml:22 still says "The skill's check-genome.mjs", while its four siblings now say "uipath-build-from-genome's".

CLI verb reachability: I could not run scripts/check-cli-verbs.py here because the command needed approval. None of the changed tasks has a command_executed criterion (only command_not_executed), so this check has nothing to verify.

Conclusion

  • ⚠ 5 tasks have issues, max severity Medium. The missing passing-run claim is High. Advisory only — not blocking merge.

@RaduAna-Maria
RaduAna-Maria added this pull request to stack #4331 November 3, 2026 16:13
@RaduAna-Maria
RaduAna-Maria marked this pull request as draft November 3, 2026 16:13
@RaduAna-Maria RaduAna-Maria changed the title Resolve planner contradictions and give each rule one home (6/6) [PILOT-9071] Run every product through one planner path and carry refactor decisions to the build (6/6) [PILOT-9071] Nov 3, 2026
@github-actions

github-actions Bot commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

skill-lint: 0 new errors, 3 new warnings

Rule Location Message
warning LINK-ANCHOR skills/uipath-planner/assets/templates/case-sdd-template.md:107 anchor '#⁠stage--stage_name-stage_id' not found in this file
warning LINK-ANCHOR skills/uipath-planner/assets/templates/case-sdd-template.md:108 anchor '#⁠secondary-stage-secondary_stage_name-stage_id' not found in this file
warning AGENT-READ-TRUNCATED skills/uipath-planner/references/extract/extract-guide.md:1 42,621 bytes, 230 lines: Codex keeps 10,000 tokens (40,000 bytes) of one read. Split it or route to smaller files
What these rules check
  • AGENT-READ-TRUNCATED: Markdown files an agent reads should fit in one read of each target agent. Each agent caps what one read returns. Codex keeps 10,000 tokens, counted as UTF-8 bytes / 4, and drops the middle. Delegate's ReadFile, which LoadSkill also uses, returns the first 2,000 lines and at most 100,000 characters of them. Claude Code's Read returns the first ~25,000 tokens with a partial-view notice and, by default, refuses a whole file over 256 KB. Gemini CLI's read_file returns the first 2,000 lines and cuts lines over 2,000 characters. Past a cap the agent sees part of the file unless it reads it in pages. Split the file, or move detail into smaller references the skill routes to. SKILL.md is checked for Codex and Delegate only: Claude Code and Gemini load it whole when the skill activates. Claude Code's count is real tokens, estimated with claude_code_bytes_per_token; the others are exact.
  • LINK-ANCHOR: #fragment links must match a heading (GitHub slug rules) or an <a id> in the target file. A wrong fragment still opens the file, so nothing looks broken, but the agent lands at the top instead of the section it was sent to. Slugs follow GitHub: underscores are kept, separators do not collapse (## A — B is #a--b), duplicates get -1, -2.

Only what this PR adds is listed, compared with the commit it branched from; issues already on the base branch are not. Updated on every push.

@RaduAna-Maria
RaduAna-Maria force-pushed the feat/genome-stack-6-planner-cleanup branch from 50de7c8 to de270bd Compare November 4, 2026 13:34
@RaduAna-Maria RaduAna-Maria changed the title Run every product through one planner path and carry refactor decisions to the build (6/6) [PILOT-9071] Update CI, docs and repo scripts for the genome split (6/6) [PILOT-9071] Nov 4, 2026
@RaduAna-Maria
RaduAna-Maria force-pushed the feat/genome-stack-6-planner-cleanup branch 2 times, most recently from d16cfb8 to 99a33c2 Compare November 4, 2026 16:15
@RaduAna-Maria
RaduAna-Maria force-pushed the feat/genome-stack-6-planner-cleanup branch from 039379d to 3e893de Compare November 11, 2026 09:25

@danmunteanu1 danmunteanu1 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Commented · 11 blockers · 20 non-blockers
Re-review at 3e893de1d. The stack was rewritten with the builder named uipath-genome again. The rename is pure: at c90f2ebed the tree equals the reviewed 039379d5a apart from the name, the SKILL.md heading and one task id. 69a7b710a moves the refactor questions into extraction and adds the Decided: project chain; 3e893de1d drops the legacy-name handling.

Fixed

  • The builder is uipath-genome throughout. Thanks.
  • Decided: sub-projects: the chain names the projects the build creates (the queues between them are new, below).
  • What leaves edit on a designed genome has one home, the edit guide's § Any genome.
  • A design change on a designed genome ends in edit's "The SDD was revised", not author.
  • The SDD hand-over sentence stated twice in the planner's SKILL.md.
  • Live application has a Recommended answer for every genome.
  • The builder's copy of the Decision Tree is gone; the rule file's other copies stay open.

Still open (threads unchanged)

  • A retired skill name stops the build (builder build-guide.md:9).
  • The builder, not the genome, decides which behaviour the rebuild follows (genome-reading-guide.md:154).
  • Rule 5 against the decided values (configuration-questions-guide.md:52).
  • The #4506 port: finding a workflow through the earlier build's hand-off (execution-guide.md:68).
  • The #4519 port: choices the source never faced (configuration-questions-guide.md:50).
  • A child SDD listed by bare filename is not fingerprinted (sdd-fingerprint.mjs:20).
  • Required Windows smoke: it runs --tags smoke, and neither builder task tagged windows (build_component, the new decided_chain_projects) carries smoke.
  • A stale or hand-edited genome builds unchecked (builder execution-guide.md:25).

New

  • 🔴 A chain of three projects has no queue design; the PR's fixture holds two queues for one unit.
  • 🔴 A genome extracted for documentation is refactored on its source's products, with no target question.
  • 🔴 A migration asks Fold, and its build ignores the answer.
  • 🔸 Three non-blockers inline.

Checks at 3e893de1d: links, flavors, descriptions and skill status pass. skills:test fails the same 21 tests as main. The planner and builder helper tests pass except the known Windows-only fingerprint test. CI had not started the pull-request workflows on this head when this was written. Pack UiPath/migration-source-frameworks#110 needs the builder name back and now conflicts with its main (review there).

## Refactor questions

Asked after the genome questions and before the split questions ([configuration-questions-guide.md](configuration-questions-guide.md)): the target of each component decides which split and scaffolding questions apply. Options are prepared from the genome — its steps, Transactional Shape and Handoffs — and from the Source Map's deployed-state and runtime rows (§ Provenance):
Asked after the genome questions and before the split questions ([configuration-questions-guide.md](configuration-questions-guide.md)). The targets are the genome's: each component is built on the product and project its Components and Build With rows name, and those targets decide which split and scaffolding questions apply. Options are prepared from the genome — its steps, Transactional Shape and Handoffs — and from the Source Map's deployed-state rows (§ Provenance):

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 Blocker · A genome extracted for documentation is refactored on its source's products, with no target question

Retire, Fold and Target are now asked only by the planner's extract Step 6c, and only for a refactor or migration: "a documentation-only extraction asks none". This guide no longer asks them. The usual path for a UiPath source is to extract it for review and decide to refactor later: the user points at that genome and asks to refactor it, which reaches this guide. That genome's Build With rows record the source's own products. The refactor then rebuilds a Windows project as Windows and a connector-only process as an RPA process, and never offers the planner's § Refactor Targets hosts. On main, every refactor build asked Target per component.

Fix: a refactor build of a genome with no Requested change row first goes to uipath-planner edit to ask the refactor questions (Step 6c), then builds; the planner's edit guide gets that row.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

e9efd78c7 closes the gap for an attended extraction by asking Retire, Fold and Target in every extraction. That has two costs:

  • An unattended extraction records the Recommended answers as the user's decisions. Step 6c takes every Recommended option and "The Requested change row records every answer as the user's decision". The build then answers them from the genome and never asks (refactor-guide.md rule 2). Example: an unattended "document this solution" folds a reader into its writer (Fold is Recommended). A refactor build months later then drops the reader's trigger and handoff, and nobody chose that.
  • A documentation request pays for a rebuild it did not ask for: two or three questions per component plus the delivery-model question. Its Build With rows can also name a recommended target instead of the product the automation runs on today.

Fix: keep Step 6c for a refactor or migration request. A refactor build of a genome with no Requested change row goes to uipath-planner edit for Step 6c first, as in the original fix. If every genome should carry a target design, record an unattended run's answers as (default) in the row, and have the build ask any (default) topic.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reproduced at bcf20b12a, on the PR's own extract_component fixture (InvoiceIntake, a Windows project):

  1. "Document what the project does … unattended" wrote Requested change | — (documentation request) | Target: InvoiceIntake → RPA process (Portable) — refactor answers, unattended Recommended default.
  2. An attended "Build the automation described in invoice-intake-genome.md" then treated it as decided, 2 of 2 runs. The opening question read "rebuilt as a Portable RPA process", the build plan read "Target: one RPA process, Portable … (from the refactor answers: the genome's Build With row)", and both runs created the project with "targetFramework": "Portable". The runtime was never asked.

An attended refactor request ("Refactor it to current UiPath practice and build…") also skipped Step 6c: no Retire, Fold, Target or delivery-model question, and the row records "Target: … Portable (the refactor answers; unattended run, Recommended option)" in a session that could ask. An attended solution extraction did ask Target and Fold (1 run each).

return [[], false];
}

const DECIDED_CHAIN = /:\s+([^:]*→[^:]*|[A-Za-z][\w.-]*)\s*$/;

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔸 Non-blocker · A chain written with -> or commas passes strict, and the build makes the default two projects

Probed at 3e893de1d on the PR's fixture: B, one invoice — the SDD §10: InvoiceDispatcher -> InvoicePerformer and …: InvoiceDispatcher, InvoicePerformer and InvoiceReporter both pass strict. The builder then finds no chain and names the projects <Component>.Dispatcher and <Component>.Performer.

Fix: on a B line, fail a list after the source's last : (->, ,, and) that is not →-separated.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed for names that start with a capital and hold no space (e9efd78c7). Two forms still pass strict and build the default two projects. Both were probed on the PR's fixture:

  • …: Invoice Dispatcher -> Invoice Performer -> Invoice Reporter
  • …: invoiceDispatcher, invoicePerformer and invoiceReporter

DECIDED_LIST matches only [A-Z][\w.-]* names.

Fix: match any name text between the separators (no : and no →), so these fail too.

@RaduAna-Maria
RaduAna-Maria force-pushed the feat/genome-stack-6-planner-cleanup branch from 3e893de to f85a765 Compare November 11, 2026 10:00

@danmunteanu1 danmunteanu1 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Commented · 13 blockers · 21 non-blockers
Re-review at f85a7650b: the stack rebased onto main ec2a62b26, and f85a7650b ports what main brought in.

Verified

  • The port: every line #4613, #4581, #4529, #4534, #4463 and #4533 added to the genome and planner skills is at this head, a few in the stack's wording. #4529's case Build handoff row stays out, since the stack dropped that row before.
  • Links, flavors, descriptions and skill status pass; skills:test fails the same 18 tests as main ec2a62b26.
  • "Run skill smoke tests" passes now. "Run RPA skill smoke tests (Windows)" still fails with "No task.json files found" (the open build_component.yaml:9 thread).

New

  • 🔴 The required activation gate fails under uipath-genome, on the same three rows in both runs (inline on activation_gate.py:81). I could not reproduce it in Claude Code itself, so I read it as the gate's harness, not routing; the gate still has to pass.
  • 🔴 The required README status check fails: the status row sits where uipath-build-from-genome sorted (inline on #4327).
  • 🔸 #4327 alone fails Test Helpers (test_genome_check.py reads the planner's skill-mapping-guide.md, which arrives in #4328) and the package build; both pass at this head. That is fine if the stack merges as one, not if #4327 merges first.

Still open: the 11 blockers of the previous re-review, threads unchanged.

Comment thread tests/scripts/activation_gate.py Resolved

@danmunteanu1 danmunteanu1 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Commented · 3 blockers · 4 non-blockers
Re-review at bcf20b12a, covering e9efd78c7, fc0dd41b5 and bcf20b12a on top of f85a7650b.

Verified

  • Links, flavors, descriptions and skill status with --check-readme pass. skills:test fails the same 18 tests as main ec2a62b26. The planner's 238 Python tests pass on Windows, the CRLF ones included.
  • The activation gate passes under uipath-genome, measured under that name (thread resolved, with the cause confirmed).
  • Every file and section the copies table names exists on both sides. Main's rules 7, 14 and 17 are back as rules 12 to 14.
  • Strict fails a chain written with -> or as a comma list. Two forms still pass (thread kept open).
  • "Run RPA skill smoke tests (Windows)" passes with the new smoke_build task; that thread is resolved.

Fixed: 27 threads, resolved.

Still open

  • 🔴 A stale or hand-edited genome still builds unchecked (builder execution-guide.md, posted 11-10). That thread has no reply yet.
  • 🔴 The retired-name rule now builds uipath-coded-agents through uipath-rpa (the retired-name thread on #4327).
  • 🔴 Every extraction now asks the refactor questions, and an unattended run records the defaults as the user's decisions (the refactor-guide.md:20 thread).
  • 🔸 The case SDD missing on disk, and the examples no read plan opens: the rebuttals stand.

New

  • 🔸 § Source values restates the migration preflight's disagreement rule (inline).
  • The floor for this skill's gate leg is now 50%. At the gate's context size every plugin skill is listed by name only, so the leg guards little until the gate scores descriptions. That is a change to the gate, not to this PR.

2. A check whose failure the source logs as a pass or ignores is a decision or an optional wait, not a hard check; a check that passes when its target is absent asserts absence.
3. A value bound to a built-in (the run date, the user's folder) is computed at run time, never taken from a same-named project variable's stored default.

Where the genome and the source disagree, the build follows the source, with the exceptions that step lists. Each disagreement is a genome deviation in the group report — step, source object and line, genome says, source says — and the genome is left to a `uipath-planner` edit.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔸 Non-blocker · Restates the migration preflight's disagreement rule

source-migration-guide.md § Migration preflight step 4 already says it: "Where the genome and the source disagree, the kind of disagreement decides what the build follows; each is recorded as a genome deviation in the group report, and the genome is left to a uipath-planner edit." This copy says "follows the source" with exceptions, so the two can drift apart.

Fix:

Suggested change
Where the genome and the source disagree, the build follows the source, with the exceptions that step lists. Each disagreement is a genome deviation in the group report — step, source object and line, genome says, source says — and the genome is left to a `uipath-planner` edit.
Where the genome and the source disagree: [source-migration-guide.md § Migration preflight](source-migration-guide.md) step 4.

@danmunteanu1

Copy link
Copy Markdown
Collaborator

Down to what we'd want before merging the stack:

  1. Refactor answers recorded without asking, then applied by the build (refactor-guide.md:20 thread).
  2. § Source values restating the migration preflight's step 4 (genome-reading-guide.md thread).
  3. UiPath/migration-source-frameworks#110 merged together with the stack: rebased on pack main, the preflight's check-genome line dropped (the build no longer runs the checker), the smoke tasks grading through skills/uipath-planner/scripts/check-genome.mjs, and the builder named uipath-genome. Pack main's smoke tasks call the check-genome.py this stack deletes.

The other open threads (retired uipath-coded-agents, the sdd-sha256 warning, the two chain forms) are fine as follow-ups.

@RaduAna-Maria
RaduAna-Maria force-pushed the feat/genome-stack-6-planner-cleanup branch 4 times, most recently from 6e0c850 to 71a9d7e Compare November 12, 2026 08:57
Base automatically changed from feat/genome-stack-5-studioweb-flavors to main November 12, 2026 08:57
RaduAna-Maria and others added 11 commits November 12, 2026 10:57
The planner and genome checker pytest jobs (Node for check-genome.mjs),
the smoke and activation-gate scripts, the Studio Web flavor contract
test and the genome docs follow the new skill layout.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…store the live-healing guide

The checker's own tests move under tests/tasks/uipath-genome, so the
builder's owners review them; the two cross-skill contract tests keep their
place with owner lines naming both teams, and the fingerprint test runs in the
job that sets up node. The required job keeps its name, with a comment saying
why.

.claude/rules/genome.md replaces the deleted uipath-genome/CLAUDE.md for both
skills: subject homes, the rules that still apply, and the files a format,
file-kind, building-skill or fingerprint change must touch together.
docs/guides/live-healing-pass.md comes back from main as the guide for
supervising a live build, linked from the builder's README row.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 65 dated from runs under its first name. Three runs on the stack top scored
13/13, 13/13 and 12/13; 90 is the nearest 5% below the lowest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…enome as written

The planner writes every genome, so it now checks each one: author, extract and
edit end with the strict check and fix every FAIL (at most three rounds), and a
new check verb reports findings. Whenever an SDD changes, the planner updates
its genome and checks it in the same run, and strict fails a Designed in: line
whose fingerprint no longer matches, so a stale genome never reaches a build.

uipath-genome ships no script: it reads the facts its read plans
branch on straight from the genome, with no context call, FAIL sorting or
fingerprint comparison, and routes check or validate requests to the planner.
Tests, the check_genome task, activation rows, CI paths, CODEOWNERS and the
genome rule file follow the script.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…cided: project chain

Refactor and migration extractions now ask Retire, Fold and Target per
component, with the planner's own Decision Tree and delivery-model rule, and
write the answers as the genome's target design; the builder builds the
targets the genome names and keeps only run modes, run record, connections and
defect rulings, dropping its copy of the Decision Tree.

A B flow's Decided: line can name its project chain
(B, <unit> — <source>: <Project> → <Project> …); the planner writes it from
the SDD, the strict check validates it, and the build creates exactly those
projects in that order. author no longer asks whether the UI application is
reachable; the build asks. Execution autonomy is defined once per skill, the
designed-genome edit list has one home, "the build" and "the lead agent"
replace execution, executor and orchestrator, the builder trims its Shape
Rules and repeats, and the fingerprint code lives once in sdd-fingerprint.mjs.
New tasks cover an SDD revise updating its genome and a Decided chain reaching
the build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…gain

uipath-genome is the current builder name, so the checker no longer treats it as
a legacy builder (uipath-genome-builder stays one), and the builder and planner
stop saying an older genome names it. An older preamble is the one asking for
Execute mode.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…changes into the split

Main #4613 names which side a bare "platform" means; the sentences now live in
the planner's extraction and format guides and the builder's execution,
refactor and migration guides. The BPMN template gets #4581's builder-SDK HITL
and project-structure blocks with their Studio Web overrides, and the skill
table's BPMN row matches main in multi-skill-patterns-guide.md, where the stack
keeps the table. The case template gets #4529's validation-row block and
#4534's stage-link ToC, and the case data guide states #4463's "any"
escalation, so the twin parity test holds. author now runs only when no genome
exists yet; an existing one is updated through edit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rgets and CI

Builder: a retired skill name builds through uipath-rpa instead of stopping
the build; the genome's Rebuild follows cell decides a defect's behaviour; a
decided-values table answers the SDD's and the request's decisions under their
own labels; building into a project finds renamed workflows through the
earlier hand-off; the source's values never answer a choice the source never
faced; every build applies Retired and Folded rows; a refactor's capability
probe runs before the plan fixes the shape.

Planner: every extraction of a UiPath source asks Retire, Fold and Target, so
every genome carries a target design; one statement of what leaves edit for
design on a designed genome; a Decided: chain of N projects uses N - 1 queues
and may come from the refactor answers; a solution root links each child SDD,
and the fingerprint also finds bare filenames; Word PDDs fall back to PDF or
pasted text.

Checks and CI: strict fails a project chain not written with arrows; the
checker drops the last legacy builder name; a Windows smoke task builds a
small genome; the README row sorts where main has it; genome.md lists the
copies both skills keep and restores main's rules 7, 14 and 17, with owners;
the activation gate can keep its rows' transcripts and uploads them when a
leg fails.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…'s verb does

The builder's Source values keeps only what changes the build; each Running in
Parts keeps the core both verbs need and drops what only the other verb uses.
The rule file's copies table says what each side keeps.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two runs on its 11 rows scored 8/11 and 7/11: at the gate's context size the
listing carries names only, and on implement, execute and run-the-migration
prompts the agent reads the genome before invoking the skill.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RaduAna-Maria
RaduAna-Maria force-pushed the feat/genome-stack-6-planner-cleanup branch from 71a9d7e to 0da9096 Compare November 12, 2026 08:57
@RaduAna-Maria
RaduAna-Maria merged commit a4ccda0 into main Nov 12, 2026
3 checks passed
@RaduAna-Maria
RaduAna-Maria deleted the feat/genome-stack-6-planner-cleanup branch November 12, 2026 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants